Prevent client secrets and proxy credentials from being logged in Microsoft Graph hook logs#59688
Conversation
a8fafc1 to
8e45f9d
Compare
4c4d6a6 to
e6276ea
Compare
providers/microsoft/azure/src/airflow/providers/microsoft/azure/hooks/msgraph.py
Outdated
Show resolved
Hide resolved
e6276ea to
7755235
Compare
providers/microsoft/azure/src/airflow/providers/microsoft/azure/hooks/msgraph.py
Outdated
Show resolved
Hide resolved
providers/microsoft/azure/src/airflow/providers/microsoft/azure/hooks/msgraph.py
Outdated
Show resolved
Hide resolved
23d0833 to
6f78a11
Compare
amoghrajesh
left a comment
There was a problem hiding this comment.
We are almost there, one comment
9f3db7c to
c33e3e4
Compare
providers/microsoft/azure/src/airflow/providers/microsoft/azure/hooks/msgraph.py
Outdated
Show resolved
Hide resolved
3b307d7 to
05525d1
Compare
amoghrajesh
left a comment
There was a problem hiding this comment.
One comment, otherwise LGTM
providers/common/compat/src/airflow/providers/common/compat/sdk.py
Outdated
Show resolved
Hide resolved
b3cb3da to
39479cd
Compare
text at INFO level.
parameter to automatically mask proxy configurations containing credentials.
Re-export redact from airflow.sdk.log and add to compat module import map to enable unconditional import via airflow.providers.common.compat.sdk
….secrets_masker to the import fallback chain for redact to support compact 3.0.6 and 3.1.5 environments
DEFAULT_SENSITIVE_FIELDS in secrets_masker to ensure proxy configurations are treated as sensitive by default regardless of field naming convention.
39479cd to
2c6b2c1
Compare
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker a9dea6d v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
…ogged in Microsoft Graph hook logs (apache#59688) Prevent client secrets and proxy credentials from being logged in Microsoft Graph hook logs (apache#59688) (cherry picked from commit a9dea6d)
…rosoft Graph hook logs (apache#59688) Prevent client secrets and proxy credentials from being logged in Microsoft Graph hook logs (apache#59688)
…rosoft Graph hook logs (apache#59688) Prevent client secrets and proxy credentials from being logged in Microsoft Graph hook logs (apache#59688)
…rosoft Graph hook logs (apache#59688) Prevent client secrets and proxy credentials from being logged in Microsoft Graph hook logs (apache#59688)
|
Is this related to https://nvd.nist.gov/vuln/detail/CVE-2025-68675 |
|
Can we please get a confirmation on above if it is a targeted fix for - CVE-2025-68675 ? |
|
Yeah. It is. We have not linked the PR to the CVE (we usually do) - we will also fix it in the CVE announcement itself. Thanks for asking @heepengpeng @kravii |
The CVE should be updated shortly to contain link to that PR |
|
thanks a lot for the confirmation @potiuk. |
…rosoft Graph hook logs (apache#59688) Prevent client secrets and proxy credentials from being logged in Microsoft Graph hook logs (apache#59688)
Problem
The
KiotaRequestAdapterHookwas logging sensitive information at INFO level:http://user:pass@proxy.example.com:3128) were logged in plain textFix
DEFAULT_SENSITIVE_FIELDSin the shared secrets_maskerredact(proxies, name="proxies")to automatically mask proxy configurations containing credentialsredact(client_secret, name="client_secret")to mask client secretsTesting
KiotaRequestAdapterHookand following is the screenshot of the task logs:^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.